<!DOCTYPE html>
<html lang="en">
<head>
	<meta charset="UTF-8">
	<meta http-equiv="X-UA-Compatible" content="IE=edge">
    <meta name="viewport" content="width=device-width, initial-scale=1">
	<title>Lifecycle policy updates | ElasticSearch 7.7 权威指南中文版</title>
	<meta name="keywords" content="ElasticSearch 权威指南中文版, elasticsearch 7, es7, 实时数据分析，实时数据检索" />
    <meta name="description" content="ElasticSearch 权威指南中文版, elasticsearch 7, es7, 实时数据分析，实时数据检索" />
    <!-- Give IE8 a fighting chance -->
    <!--[if lt IE 9]>
    <script src="https://oss.maxcdn.com/html5shiv/3.7.2/html5shiv.min.js"></script>
    <script src="https://oss.maxcdn.com/respond/1.4.2/respond.min.js"></script>
    <![endif]-->
	<link rel="stylesheet" type="text/css" href="../static/styles.css" />
	<script>
	var _link = 'update-lifecycle-policy.html';
    </script>
</head>
<body>
<div class="main-container">
    <section id="content">
        <div class="content-wrapper">
            <section id="guide" lang="zh_cn">
                <div class="container">
                    <div class="row">
                        <div class="col-xs-12 col-sm-8 col-md-8 guide-section">
                            <div style="color:gray; word-break: break-all; font-size:12px;">原英文版地址: <a href="https://www.elastic.co/guide/en/elasticsearch/reference/7.7/update-lifecycle-policy.html" rel="nofollow" target="_blank">https://www.elastic.co/guide/en/elasticsearch/reference/7.7/update-lifecycle-policy.html</a>, 原文档版权归 www.elastic.co 所有<br/>本地英文版地址: <a href="../en/update-lifecycle-policy.html" rel="nofollow" target="_blank">../en/update-lifecycle-policy.html</a></div>
                        <!-- start body -->
                  <div class="page_header">
<strong>重要</strong>: 此版本不会发布额外的bug修复或文档更新。最新信息请参考 <a href="https://www.elastic.co/guide/en/elasticsearch/reference/current/index.html" rel="nofollow">当前版本文档</a>。
</div>
<div id="content">
<div class="breadcrumbs">
<span class="breadcrumb-link"><a href="index.html">Elasticsearch Guide [7.7]</a></span>
»
<span class="breadcrumb-link"><a href="index-lifecycle-management.html">ILM: Manage the index lifecycle</a></span>
»
<span class="breadcrumb-link"><a href="ilm-concepts.html">ILM concepts</a></span>
»
<span class="breadcrumb-node">Lifecycle policy updates</span>
</div>
<div class="navheader">
<span class="prev">
<a href="index-rollover.html">« Rollover</a>
</span>
<span class="next">
<a href="getting-started-index-lifecycle-management.html">Tutorial: Automate rollover with ILM »</a>
</span>
</div>
<div class="section xpack">
<div class="titlepage"><div><div>
<h2 class="title">
<a id="update-lifecycle-policy"></a>Lifecycle policy updates<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch/edit/7.7/docs/reference/ilm/update-lifecycle-policy.asciidoc">edit</a><a class="xpack_tag" href="https://www.elastic.co/subscriptions"></a>
</h2>
</div></div></div>

<p>You can change how the lifecycle of an index or collection of rolling indices is managed
by modifying the current policy or switching to a different policy.</p>
<p>To ensure that policy updates don’t put an index into a state where it can’t exit the current phase,
the phase definition is cached in the index metadata when it enters the phase.
This cached definition is used to complete the phase.</p>
<p>When the index advances to the next phase, it uses the phase definition from the updated policy.</p>
<h3>
<a id="ilm-apply-changes"></a>How changes are applied<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch/edit/7.7/docs/reference/ilm/update-lifecycle-policy.asciidoc">edit</a>
</h3>
<p>When a policy is initially applied to an index, the index gets the latest version of the policy.
If you update the policy, the policy version is bumped and ILM can detect that the index
is using an earlier version that needs to be updated.</p>
<p>Changes to <code class="literal">min_age</code> are not propagated to the cached definition.
Changing a phase’s <code class="literal">min_age</code> does not affect indices that are currently executing that phase.</p>
<p>For example, if you create a policy that has a hot phase that does not specify a <code class="literal">min_age</code>,
indices immediately enter the hot phase when the policy is applied.
If you then update the policy to specify a <code class="literal">min_age</code> of 1 day for the hot phase,
that has no effect on indices that are already in the hot phase.
Indices created <em>after</em> the policy update won’t enter the hot phase until they are a day old.</p>
<h3>
<a id="ilm-apply-new-policy"></a>How new policies are applied<a class="edit_me edit_me_private" rel="nofollow" title="Editing on GitHub is available to Elastic" href="https://github.com/elastic/elasticsearch/edit/7.7/docs/reference/ilm/update-lifecycle-policy.asciidoc">edit</a>
</h3>
<p>When you apply a different policy to a managed index,
the index completes the current phase using the cached definition from the previous policy.
The index starts using the new policy when it moves to the next phase.</p>
</div>
<div class="navfooter">
<span class="prev">
<a href="index-rollover.html">« Rollover</a>
</span>
<span class="next">
<a href="getting-started-index-lifecycle-management.html">Tutorial: Automate rollover with ILM »</a>
</span>
</div>
</div>

                  <!-- end body -->
                        </div>
                        <div class="col-xs-12 col-sm-4 col-md-4" id="right_col">
                        
                        </div>
                    </div>
                </div>
            </section>
        </div>
    </section>
</div>
<script src="../static/cn.js"></script>
</body>
</html>